Guys, when this update will be merged?

Could somebody merge this pull request please? The angular-seed project do not use the latest Angular1 Version.

@petebacondarwin Please merge this so we can use 1.3.x by default.

Blimey, I can't believe we didn't do this already. We are about to release 1.4.0 so how about we just wait and bump to that instead?

@petebacondarwin Sounds good - looking forward to 1.4. Keep up the great work.

As 1.4 is quite different to 1.3.x are we sure this is the right thing to do at this time?
Even so, to have a 1.3.x version of the seed is highly desirable anyhow - no?

Please check out the migration path from 1.3 to 1.4. I don't think it is particularly painful and 1.4 offers many nice new things. Given that angular-seed is only a starter then one could consider that people should only be using it for new projects, in which case there would be very limited migration. I suspect that the changes from 1.3 to 1.4 barely affect any of the angular-seed starter code at all.

If you already have a project based on top of angular-seed then, it is a piece of cake to change the bower.json to reference 1.3 instead of 1.2 if you want. You just change the dependencies and re-run bower install. Then make sure that changes between 1.2 and 1.3 don't cause problems in your app.

My preference is that the seed project should run off the latest stable version.

@petebacondarwin I agree absolutely, seed project should run off the latest stable version.

I think having an official seed project on a non-updated stable version does not really reflects well the maturity of the Angular project and it's dev community. Even a new version is almost at the door, why not merge this very simple request right away? No harm done, IMO.

Anyway, I didn't took notice of this PR and went forward with one here #278. I've also updated html5-boilerplate and karma on package.json.

Cheers.

I guess angular-seed is not maintained anymore. That is a pity.

It should have been based on 1.3 since more than half a year. It should have been based on 1.4 since a couple of weeks.

@jgehrcke Here's a detailed collection/comparison of over 100 alternatives in excruciating detail.

It's actually a really good thing when projects fall by the wayside, the number of alternatives reduces and people are united.

@dancancro I did not access your "secret" document, and I think I do not need/want to read it. AngularJS is popular for a reason, and it will stay popular. The angular-seed project therefore is very important. My point (and I suppose the intention of everybody who contributed to this thread) is not that we should give up on angular-seed, but that we want to support it, and encourage it to follow the pretty quick developments of the main line.

Edit: maybe I was a little rude here. Only now I see that you have put a real effort in communicating that there are just too many seed projects. Please excuse, it was not easy to grasp from your short message. I believe that the "official" seed project should be well-supported. Just because it is official. I have never looked at alternatives.

@jgehrcke It's up to you.

The document isn't secret. You just have to chip in some knowledge about something and you can open it. It's a knowledge sharing system. We're all in this together.

Just to clarify, the document isn't anti-Angular. It profiles 123 different things you can use to start making a web application and 89 of them use AngularJS. These are alternatives to angular-seed, not alternatives to AngularJS.

Best of luck with angular-seed. I'm going to keep trying to convince people programming isn't religion and you are allowed to question and compare approaches on merit. If you're curious (or if you're not curious) from my analysis, angular-seed comes in number 46 on the list based on the benefit it provides.

We are now on 1.4.0. Sorry for the delay :-)